User interfaces for location-related communications

ABSTRACT

The present disclosure generally relates to managing location-related communications of an electronic device associated with a user account.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Nonprovisional applicationSer. No. 16/669,187, entitled “User Interfaces for Location-RelatedCommunications,” filed Oct. 30, 2019, which claims the benefit of U.S.Provisional Application No. 62/856,005, entitled “User Interfaces forLocation-Related Communications,” filed Jun. 1, 2019, the contents ofeach of which are hereby incorporated by reference in their entireties.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for managing location-relatedcommunications of an electronic device associated with a user account.

BACKGROUND

An electronic device can include hardware and/or software foridentifying the current location of the electronic device. Such a devicecan also communicate its location to one or more other devices.

BRIEF SUMMARY

Some techniques for managing location-related communications of anelectronic device associated with a user account using electronicdevices, however, are generally cumbersome and inefficient. For example,some existing techniques use a complex and time-consuming userinterface, which may include multiple key presses or keystrokes.Existing techniques require more time than necessary, wasting user timeand device energy. This latter consideration is particularly importantin battery-operated devices. Existing techniques may also not providesufficient notice and security for sensitive, location-relatedcommunications.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for managinglocation-related communications of an electronic device associated witha user account. Such methods and interfaces optionally complement orreplace other methods for managing location-related communications of anelectronic device associated with a user account. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

Example methods are described herein. An example method includes, at anelectronic device having a display device: while the electronic deviceis associated with a first user account that shares a location of theelectronic device with one or more user accounts other than the firstuser account: receiving an indication that a second user account isrequesting to be notified about changes in location of the electronicdevice relative to a first geographic location that satisfy a set ofcriteria; and after receiving the indication that the second useraccount is requesting to be notified about changes in the location ofthe electronic device relative to the first geographic location thatsatisfy the set of criteria: in accordance with a determination that aset of notification criteria are satisfied, the set of notificationcriteria including a criterion that is satisfied when the indicationthat the second user account is requesting to be notified has beenreceived, displaying, via the display device, a notification indicatingthat the second user account is requesting to be notified about changesin the location of the electronic device relative to the firstgeographic location that satisfy the set of criteria.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device, the one ormore programs including instructions for: while the electronic device isassociated with a first user account that shares a location of theelectronic device with one or more user accounts other than the firstuser account: receiving an indication that a second user account isrequesting to be notified about changes in location of the electronicdevice relative to a first geographic location that satisfy a set ofcriteria; and after receiving the indication that the second useraccount is requesting to be notified about changes in the location ofthe electronic device relative to the first geographic location thatsatisfy the set of criteria: in accordance with a determination that aset of notification criteria are satisfied, the set of notificationcriteria including a criterion that is satisfied when the indicationthat the second user account is requesting to be notified has beenreceived, displaying, via the display device, a notification indicatingthat the second user account is requesting to be notified about changesin the location of the electronic device relative to the firstgeographic location that satisfy the set of criteria.

Example transitory computer-readable storage media are described herein.An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while the electronic device is associatedwith a first user account that shares a location of the electronicdevice with one or more user accounts other than the first user account:receiving an indication that a second user account is requesting to benotified about changes in location of the electronic device relative toa first geographic location that satisfy a set of criteria; and afterreceiving the indication that the second user account is requesting tobe notified about changes in the location of the electronic devicerelative to the first geographic location that satisfy the set ofcriteria: in accordance with a determination that a set of notificationcriteria are satisfied, the set of notification criteria including acriterion that is satisfied when the indication that the second useraccount is requesting to be notified has been received, displaying, viathe display device, a notification indicating that the second useraccount is requesting to be notified about changes in the location ofthe electronic device relative to the first geographic location thatsatisfy the set of criteria.

Example electronic devices are described herein. An example electronicdevice includes a display device; one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:while the electronic device is associated with a first user account thatshares a location of the electronic device with one or more useraccounts other than the first user account: receiving an indication thata second user account is requesting to be notified about changes inlocation of the electronic device relative to a first geographiclocation that satisfy a set of criteria; and after receiving theindication that the second user account is requesting to be notifiedabout changes in the location of the electronic device relative to thefirst geographic location that satisfy the set of criteria: inaccordance with a determination that a set of notification criteria aresatisfied, the set of notification criteria including a criterion thatis satisfied when the indication that the second user account isrequesting to be notified has been received, displaying, via the displaydevice, a notification indicating that the second user account isrequesting to be notified about changes in the location of theelectronic device relative to the first geographic location that satisfythe set of criteria.

An example electronic device includes a display device; and means for,while the electronic device is associated with a first user account thatshares a location of the electronic device with one or more useraccounts other than the first user account: receiving an indication thata second user account is requesting to be notified about changes inlocation of the electronic device relative to a first geographiclocation that satisfy a set of criteria; and after receiving theindication that the second user account is requesting to be notifiedabout changes in the location of the electronic device relative to thefirst geographic location that satisfy the set of criteria: inaccordance with a determination that a set of notification criteria aresatisfied, the set of notification criteria including a criterion thatis satisfied when the indication that the second user account isrequesting to be notified has been received, displaying, via the displaydevice, a notification indicating that the second user account isrequesting to be notified about changes in the location of theelectronic device relative to the first geographic location that satisfythe set of criteria.

An example method includes, at an electronic device: while a currentlocation associated with a user account is being evaluated relative to ageographic location and a range of times: in accordance with adetermination that the current location associated with the user accountdoes not have a predefined relationship to the geographic locationduring the range of times, generating an alert indicating that thecurrent location associated with the user account does not have thepredefined relationship to the geographic location; and in accordancewith a determination that the current location associated with the useraccount does not have a predefined relationship to the geographiclocation at a time that is outside of the range of times, forgoinggeneration of an alert indicating that the current location associatedwith the user account does not have the predefined relationship to thegeographic location.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while a current location associated with auser account is being evaluated relative to a geographic location and arange of times: in accordance with a determination that the currentlocation associated with the user account does not have a predefinedrelationship to the geographic location during the range of times,generating an alert indicating that the current location associated withthe user account does not have the predefined relationship to thegeographic location; and in accordance with a determination that thecurrent location associated with the user account does not have apredefined relationship to the geographic location at a time that isoutside of the range of times, forgoing generation of an alertindicating that the current location associated with the user accountdoes not have the predefined relationship to the geographic location.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while a current location associated with auser account is being evaluated relative to a geographic location and arange of times: in accordance with a determination that the currentlocation associated with the user account does not have a predefinedrelationship to the geographic location during the range of times,generating an alert indicating that the current location associated withthe user account does not have the predefined relationship to thegeographic location; and in accordance with a determination that thecurrent location associated with the user account does not have apredefined relationship to the geographic location at a time that isoutside of the range of times, forgoing generation of an alertindicating that the current location associated with the user accountdoes not have the predefined relationship to the geographic location.

An example electronic device includes one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:while a current location associated with a user account is beingevaluated relative to a geographic location and a range of times: inaccordance with a determination that the current location associatedwith the user account does not have a predefined relationship to thegeographic location during the range of times, generating an alertindicating that the current location associated with the user accountdoes not have the predefined relationship to the geographic location;and in accordance with a determination that the current locationassociated with the user account does not have a predefined relationshipto the geographic location at a time that is outside of the range oftimes, forgoing generation of an alert indicating that the currentlocation associated with the user account does not have the predefinedrelationship to the geographic location.

An example electronic device includes means for, while a currentlocation associated with a user account is being evaluated relative to ageographic location and a range of times: in accordance with adetermination that the current location associated with the user accountdoes not have a predefined relationship to the geographic locationduring the range of times, generating an alert indicating that thecurrent location associated with the user account does not have thepredefined relationship to the geographic location; and in accordancewith a determination that the current location associated with the useraccount does not have a predefined relationship to the geographiclocation at a time that is outside of the range of times, forgoinggeneration of an alert indicating that the current location associatedwith the user account does not have the predefined relationship to thegeographic location.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing location-related communications of an electronicdevice associated with a user account, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace other methods formanaging location-related communications of an electronic deviceassociated with a user account.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-6U illustrate exemplary user interfaces for managinglocation-related communications of an electronic device associated witha user account, in accordance with some embodiments.

FIG. 7 is a flow diagram illustrating a method for managinglocation-related communications of an electronic device associated witha user account, in accordance with some embodiments.

FIG. 8 is a flow diagram illustrating a method for managinglocation-related communications of an electronic device associated witha user account, in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for managing location-related communications of anelectronic device associated with a user account. For example, a parentcan manage notifications for indicating when another device, such as achild's device that is associated with the child's user account, is notat an expected geographic location for a particular timeframe. Suchtechniques can reduce the cognitive burden on a user who manageslocation-related communications of an electronic device associated witha user account, thereby enhancing productivity. Further, such techniquescan reduce processor and battery power otherwise wasted on redundantuser inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for managinglocation-related communications of an electronic device. FIGS. 6A-6Uillustrate exemplary user interfaces for managing location-relatedcommunications of an electronic device associated with a user account.FIG. 7 is a flow diagram illustrating methods of managinglocation-related communications of an electronic device associated witha user account, in accordance with some embodiments. FIG. 8 is a flowdiagram illustrating methods of managing location-related communicationsof an electronic device associated with a user account, in accordancewith some embodiments. The user interfaces in FIGS. 6A-6U are used toillustrate the processes described below, including the processes inFIGS. 7 and 8 .

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2 ) optionally include an up/downbutton for volume control of speaker 111 and/or microphone 113. The oneor more buttons optionally include a push button (e.g., 206, FIG. 2 ).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700 and800 (FIGS. 7 and 8 ). A computer-readable storage medium can be anymedium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6U illustrate exemplary user interfaces for managinglocation-related communications of an electronic device associated witha user account, in accordance with some embodiments. The user interfacesin these figures are used to illustrate the processes described below,including the processes in FIGS. 7 and 8 . As discussed in greaterdetail below, it should be appreciated that these processes involvevarious steps that can be performed across different electronic devices.Non-limiting examples of such steps can include calculations,determinations, instructions to grant, revoke, or deny permission for anaccount to use data in a particular manner, and instructions to displayan object such as a notification or alert. In some embodiments, one ormore steps can be performed at a first electronic device (e.g.,electronic device 6000A) that includes one or more features of device100, device 300, and device 500. In some embodiments, one or more stepscan be performed at a second electronic device (e.g., electronic device6000B) that is includes one or more features of device 100, device 300,and device 500. In some embodiments, one or more steps can be performedat a third electronic device such as, for example, a server. In someembodiments, one or more steps are performed at any combination of thefirst electronic device, the second electronic device, and the thirdelectronic device.

FIGS. 6A-6U illustrate exemplary user inputs and corresponding changesto a user interface, which can be displayed on an electronic device,such as electronic device 6000, having display 6002, which in some casesis a touch-sensitive display (e.g., 112). In the present disclosure, thedescribed electronic device can be referenced using reference numbers6000, 6000A, or 6000B. In general, reference number 6000A is used torefer to a first electronic device (e.g., a parent's electronic device),reference number 6000B is used to refer to a second electronic devicethat is different from the first electronic device (e.g., a child'selectronic device), and reference number 6000 is used to referindiscriminately to the first electronic device, the second electronicdevice, or both. Similarly, various features of electronic device 6000can be referenced with an “A” or “B” designation to differentiatebetween two instances of a similar feature. For example, referencenumber 6002A is used to refer to a display component of electronicdevice 6000A, reference number 6002B is used to refer to a displaycomponent of electronic device 6000B, and reference number 6002 isgenerally used to refer to a display of electronic device 6000, which,in turn, refers indiscriminately to the display of the first electronicdevice, the display of the second electronic device, or both.

In some embodiments, the electronic devices are associated with useraccounts. For example, electronic device 6000A is an electronic devicethat is associated with a parent's user account, and electronic device6000B is an electronic device that is associated with a child's useraccount. It should be appreciated that the user accounts do not requirea particular relationship to one another, other than an authorization toshare data with at least one of the accounts. For the sake ofsimplicity, however, the following disclosure uses embodiments in whichone user account is a parent's user account and the other user accountis a child's user account. Specifically, the parent is referred to as“Mom” and the child is referred to as “Jane.” Accordingly, electronicdevice 6000A can be referred to herein as Mom's device 6000A, andelectronic device 6000B can be referred to herein as Jane's device6000B. Similarly, the parent's account can be referred to as “Mom'saccount,” and the child's account can be referred to as “Jane'saccount.” Similar nomenclature is used in other instances whereappropriate.

In some embodiments, the user accounts can be authorized to sharelocation data between the user accounts. For example, in accordance withthe present disclosure, Jane has set up her user account in a mannerthat authorizes Mom's account to receive, at one or more electronicdevices associated with Mom's account, location data indicating alocation (e.g., GPS coordinates) of one or more electronic devicesassociated with Jane's account. Thus, Jane is said to have authorizedMom to receive location data for Jane's electronic devices. Accordingly,Mom's account is authorized (by Jane's account) to manage location dataassociated with Jane's account.

The following disclosure describes various embodiments in which Mommanages location-related communications relating to Jane, which ispresumed to be represented by the location of one or more of Jane'selectronic devices (e.g., Jane's device 6000B or Jane's device 6100B),by establishing a geofence (e.g., a virtual boundary based on aparticular geographic location (e.g., a particular geographic area)) fora particular timeframe. In such embodiments, Mom is managing Jane'slocation in order to be notified (e.g., by receiving notifications atMom's device 6000A) when Jane is not at an expected location during aparticular range of times. This enables Mom to be alerted to a situationin which Jane is not at an expected location, such as at school, forexample, without the need for Mom to constantly monitor Jane's locationusing, for example, a map application. In effect, Mom can assume thatJane is at school during the specified timeframe, unless she is notifiedotherwise.

Referring now to FIG. 6A, Mom's device 6000A is shown displayinglocations management user interface 6005. Locations management userinterface 6005 includes Jane's account information 6004, which includesinformation available at Mom's device 6000A pertaining to Jane'saccount. Jane's account information 6004 includes devices listing 6006for indicating devices associated with Jane's user account, andnotifications listing 6008 for viewing and managing location-basednotifications (e.g., geofence notifications) created for Jane's account.As shown in FIG. 6A, Jane's listed devices include Jane's Phone 6006-1,which refers to Jane's device 6000B shown in FIG. 6F, and Jane's Watch6006-2, which refers to Jane's device 6100B shown in FIG. 6I.Notifications listing 6008 includes first geofence identifier 6008-1corresponding to an existing geofence notification for notifying Mom'saccount when Jane (e.g., Jane's device 6000B) arrives at home.Notifications listing 6008 also includes notification creationaffordance 6009, which can be selected to create a new geofencenotification.

As shown in FIG. 6A, Mom's device 6000A detects input 6010 (e.g., a userinput such as, for example, a tap gesture) on notification creationaffordance 6009 and, in response, displays notification creation userinterface 6012 shown in FIG. 6B.

Notification creation user interface 6012 is a user interface forcreating a geofence notification for Jane's account. As shown in FIG.6B, notification creation user interface 6012 includes location-basednotification type region 6014, location selection region 6016, timeselection region 6018, and day customization region 6020. In someembodiments, notification creation user interface 6012 can includerecurrence affordance 6022 for setting the geofence notification to be arecurring notification. In some embodiments, the geofence notificationdefaults to a recurring notification unless specified otherwise.

Location-based notification type region 6014 includes selectable optionsfor setting a notification condition for the geofence. For example,arrival notification type 6014-1 sets a condition that is satisfied whenJane arrives at a particular location (e.g., during a particular periodof time). Thus, an arrival notification type will notify Mom (e.g., bydisplaying a notification on Mom's device 6000A) when Jane arrives atthe specified location. Departure notification type 6014-2 sets acondition that is satisfied when Jane leaves a particular location(e.g., during a particular period of time). Thus, a departurenotification type will notify Mom when Jane leaves the specifiedlocation. Expected location notification type 6014-3 sets a conditionthat is satisfied when Jane is not at a particular location during aparticular time period. Thus, an expected location notification typewill notify Mom when Jane is not at the specified location at any timeduring the specified period of time. For example, a notification will betriggered if Jane is not at the specified location when the time starts,or if Jane leaves the specified location after the time period startsbut before the time period ends. As shown in FIG. 6B, the selectedgeofence notification type is expected location notification type6014-3.

Location selection region 6016 includes selectable options for setting alocation component for the selected geofence notification type (expectedlocation notification type 6014-3). In some embodiments, the locationoptions are user-defined locations that indicate a location that iswithin the boundary of the geofence (e.g., a central point for thegeofence). In FIG. 6B, the location options include home 6016-1 andschool 6016-2. Location options also include location creation option6016-3, which can be selected to create a new location. In someembodiments, a user can create a new location option by selectinglocation creation option 6016-3 and specifying the new location, whichis then added to location selection region 6016. In some embodiments,specifying the new location can include entering location information(e.g., address information, coordinates, etc.) and/or selecting alocation on a map. As shown in FIG. 6B, the selected location option isschool 6016-2. Thus, the geofence notification is configured to notifyMom if Jane is not located at school during the set timeframe.

In some embodiments, the boundary of the geofence can be adjustedrelative to any of the selected locations (e.g., home, school, or othercreated location) by adjusting the boundary of the geofence on a mapshowing the selected location. For example, Mom can select one of thelocation options to view a map of the location with a representation ofthe geofence boundary (see, for example, FIG. 6S), and can adjust theboundary (e.g., diameter) of the geofence by adjusting a zoom level ofthe displayed map while the geofence boundary remains stationary withrespect to the map display area.

Time selection region 6018 includes options for setting the timeframefor the selected geofence notification type (expected locationnotification type 6014-3). In some embodiments, the time selectionoptions include start time 6018-1 and end time 6018-2. As shown in FIG.6B, the start time is 9:00 AM, and the end time is 3:00 PM. In thisembodiment, the geofence notification is configured to notify Mom ifJane is not at school between 9:00 AM and 3:00 PM.

Day customization region 6020 includes selectable options for settingparticular days of the week that the geofence is active. As shown inFIG. 6B, options 6020-1 through 6020-5 are selected and correspond toMonday, Tuesday, Wednesday, Thursday, and Friday. Options 6020-6 and6020-7, corresponding to Saturday and Sunday, respectively, are notselected. Accordingly, the geofence notification is active on weekdays,and is inactive on weekends. Thus, the geofence notification isconfigured to notify Mom if Jane is not located at school between 9:00AM and 3:00 PM on weekdays. If Jane is not located at school at any timeoutside of 9:00 AM to 3:00 PM on a weekday, Mom will not be notified.

Recurrence affordance 6022 is set to “ON,” indicating that the geofencenotification is a recurring notification that will repeat indefinitelyor until specified otherwise. For example, the geofence will repeat on aweekly basis.

In FIG. 6B, Mom's device 6000A detects input 6024 on done affordance6026 and, in response, displays confirmation user interface 6028, asshown in FIG. 6C. Confirmation user interface 6028 summarizes theconditions of the geofence and displays create notification affordance6030 for confirming creation of the geofence and cancel affordance 6032for canceling creation of the geofence. If the geofence is confirmed(e.g., by selection of create notification affordance 6030) aninvitation is sent to Jane's account to accept the conditions of thegeofence, as discussed in greater detail below with reference to FIGS.6F-6K.

In FIG. 6C, Mom's device 6000A detects input 6034 on create notificationaffordance 6030 and, in response, displays, in FIG. 6D, Jane's accountinformation 6004 with notifications listing 6008 updated to show secondgeofence identifier 6008-2 corresponding to the geofence notificationcreated in FIGS. 6A-6C. As shown in FIG. 6D, second geofence identifier6008-2 is shown with an “Invitation Sent” status identifier 6036 whenthe geofence is pending acceptance by Jane's account. This indicatesthat Jane's account has been sent an invitation to accept the terms ofthe geofence notification, but Jane's account has not yet accepted theterms of the geofence. If Jane's account does not accept the terms ofthe geofence, Mom's account is not authorized to receive a notificationif Jane's device breaches the geofence (e.g., if Jane is not located atschool between 9 AM and 3 PM on weekdays), and the geofence will not beactivated and, in some embodiments, second geofence identifier 6008-2will be removed from notifications listing 6008. In some embodiments,Mom's account continues to receive location information for Jane'saccount, even if Jane's account does not accept the terms of thegeofence notification request. After Jane's account has accepted theterms of the geofence, status identifier 6036 is removed, as shown inFIG. 6E.

FIGS. 6F-6K illustrate various embodiments in which the invitation toaccept the terms of the geofence notification is displayed for Jane'sacceptance. In some embodiments, the invitation can be displayed onJane's device 6000B, as shown in FIGS. 6F-6H and 6K. In someembodiments, the invitation can be displayed on Jane's device 6100B, asshown in FIGS. 6I and 6J. In some embodiments, Jane's device 6100B is awearable device (e.g., a smartwatch) having display 6102B.

In some embodiments, display of the invitation (e.g., as a notification)is triggered by various conditions. For example, in some embodiments,such as that shown in FIG. 6F, the invitation is displayed when thegeofence is created by Mom's account (e.g., upon selection of createnotification affordance 6030, as shown in FIG. 6C). In some embodiments,the invitation is displayed upon creation of the geofence if thegeofence is not a recurring event (e.g., a one-time geofence). In FIG.6F, Jane's device 6000B displays lock screen user interface 6038. Lockscreen user interface 6038 includes notification 6040 displayed at 10:09AM on Saturday, June 1^(st), which is approximately the same time thatMom's account created the geofence in FIGS. 6A-6C. Notification 6040invites Jane's account to accept the conditions of the geofence createdby Mom's account, thereby authorizing Mom's account to receive anotification if Jane's device (e.g., 6000B or 6100B, depending on whichdevice is configured to represent Jane's location, for example, asconfigured at device option 6078 in FIG. 6M) breaches the geofence(e.g., if Jane is not located at school between 9 AM and 3 PM onweekdays). In some embodiments, Jane can interact with notification 6040to accept or decline the invitation to authorize the geofencenotification. If Jane accepts the invitation, Jane's account continuesto share location data with Mom's account and authorizes Mom's accountto receive a notification if Jane's device breaches the geofence. IfJane declines the invitation (or otherwise does not accept theinvitation), Jane's account continues to share location data with Mom'saccount based on prior authorization of the location data sharing, butdoes not authorize Mom's account to receive a notification if Jane'sdevice breaches the geofence.

In some embodiments, the invitation is displayed when one or more of thecomponents (e.g., the location component, the time component) specifiedby the geofence are satisfied. For example, FIG. 6G illustrates anembodiment in which notification 6040 is displayed on lock screen userinterface 6038 when the start time component of the geofence issatisfied. FIG. 6G shows two instances of Jane's device 6000B, whereineach instance of Jane's device corresponds to a particular time. Jane'sdevice 6000B-1 represents the state of Jane's device 6000B at 8:59 AM onMonday, June 3^(rd). Jane's device 6000B-2 represents the state ofJane's device 6000B at 9:00 AM on Monday, June 3^(rd). As shown in FIG.6G, notification 6040 is not displayed at Jane's device 6000B until 9:00AM on Monday, June 3^(rd), which corresponds to the start time (e.g.,9:00 AM on a weekday) set in FIG. 6B.

As another example, FIG. 6H illustrates an embodiment in whichnotification 6040 is displayed when the location component of thegeofence is satisfied. FIG. 6H shows two instances of a map and Jane'sdevice, wherein each instance of the map corresponds to an instance ofJane's device. Jane's device 6000B-3 represents a state of Jane's device6000B for a detected location of the device, which is represented by map6042-1. Jane's device 6000B-4 represents a state of Jane's device 6000Bfor a detected location of the device, which is represented by map6042-2. Each instance of the map (e.g., map 6042-1 and map 6042-2)includes geofence boundary 6044 (representing the location componentspecified for the geofence) and representation 6046 of Jane's device6000B on the map. As shown in map 6042-1, representation 6046 is notlocated within geofence boundary 6044, indicating that Jane's device6000B is not located at the location specified by the geofence.Accordingly, Jane's device 6000B-3 does not display notification 6040 onlock screen user interface 6038, because the location of Jane's device6000B does not satisfy the location component of the geofence. As shownin map 6042-2, however, representation 6046 is located within geofenceboundary 6044, indicating that Jane's device 6000B is located at thelocation specified by the geofence. Accordingly, Jane's device 6000B-4displays notification 6040 (e.g., on lock screen user interface 6038),because the location of Jane's device 6000B satisfies the locationcomponent of the geofence. In some embodiments, notification 6040 isdisplayed when both the time component and the location component of thegeofence are satisfied.

In some embodiments, the invitation can be displayed on variouselectronic devices associated with Jane's account. For example, FIGS. 6Iand 6J illustrate an embodiment in which the invitation is displayed onJane's device 6100B, which is shown as a wearable device such as, forexample, a smartwatch. In FIG. 6I, the invitation is displayed asnotification 6048, which is similar to notification 6040. Notification6048 includes text region 6048-1 displaying text inviting Jane to acceptthe conditions of the geofence created by Mom's account in FIGS. 6A-6C.Notification 6048 also includes accept affordance 6048-2, which can beselected to accept the invitation (thereby authorizing Mom's account toreceive a notification if Jane's device breaches the geofence), anddismiss affordance 6048-3, which can be selected to dismiss theinvitation without authorizing Mom's account to receive a notificationif Jane's device breaches the geofence. In some embodiments, such asthat shown in FIG. 6J, Jane's device 6100B displays user interface 6050in response to detecting selection of accept affordance 6048-2. Userinterface 6050 includes map 6052 showing a representation of thelocation of the geofence and text 6054 indicating the terms of thegeofence and confirming to Jane that she has accepted the terms of thegeofence, authorizing Mom's account to receive a notification if Jane(e.g., Jane's device 6100B or Jane's device 6000B) is not located atschool between 9 AM and 3 PM on weekdays.

In some embodiments, notification 6040 (or notification 6048) can bedismissed without immediately accepting the invitation. In suchembodiments, the invitation can be accessed (and subsequently acceptedor declined) from a locations management user interface associated withJane's account such as, for example, locations management user interface6056 shown in FIG. 6K. In some embodiments, Jane's device 6000B displayslocations management user interface 6056 in response to detecting one ormore inputs directed to a notification. For example, Jane's device 6000Bdisplays locations management user interface 6056 in FIG. 6K in responseto detecting a tap input on notification 6040 in FIG. 6H.

In FIG. 6K, Jane's device 6000B displays locations management userinterface 6056, which includes map 6058 showing locations associatedwith user accounts that are authorized to share location data withJane's account. For example, map 6058 shows representation 6060indicating a location on map 6058 that is associated with Mom's account(for example, a location of Mom's device 6000A). Locations managementuser interface 6056 also includes user accounts region 6062, whichincludes data related to the user accounts authorized to share locationdata with Jane's account. As shown in FIG. 6K, user accounts region 6062includes item 6064 representing the invitation to accept the terms ofthe geofence notification created by Mom's account in FIGS. 6A-6C. Item6064 specifies the terms of the geofence notification and includesaccept affordance 6064-1 for accepting the terms of the geofencenotification and decline affordance 6064-2 for declining the terms ofthe geofence notification. If Jane accepts the terms of the geofencenotification, Jane's account continues to share location data with Mom'saccount and authorizes Mom's account to receive a notification if Jane'sdevice breaches the geofence. If Jane declines the terms of the geofencenotification, Jane's account continues to share location data with Mom'saccount based on prior authorization of the location data sharing, butdoes not authorize Mom's account to receive a notification if Jane'sdevice breaches the geofence.

FIG. 6K depicts Jane's acceptance of the terms of the geofencenotification. Specifically, Jane's device 6000B detects input 6066 onaccept affordance 6064-1 and, in response, updates item 6064, as shownin FIG. 6L, to display text 6064-3 confirming to Jane that she hasaccepted the terms of the geofence and indicating that Mom's account isauthorized to receive a notification if Jane (e.g., Jane's device 6100Bor Jane's device 6000B) is not located at school between 9 AM and 3 PMon weekdays.

FIGS. 6L-6N illustrate various embodiments for managing geofencenotifications associated with Jane's account.

In FIG. 6L, Jane's device 6000B detects input 6068 on “Me” affordance6070 and, in response, displays notification management user interface6072, as shown in FIG. 6M. Notification management user interface 6072includes location-based notification information associated with Jane'saccount such as, for example, location information 6074 indicating adetected location associated with Jane's account (e.g., a location ofJane's device 6000B), map settings option 6076, and device option 6078for selecting a specific device that is used to determine the locationassociated with Jane's account. For example, in FIG. 6M, device option6078 indicates that Jane's location is associated with the location ofJane's device 6000B. However, in some embodiments, device option 6078can be updated to select Jane's device 6100B or other electronic devicesassociated with Jane's user account, such that the location of theselected device is associated with the location of Jane.

As shown in FIG. 6M, notification management user interface 6072 alsoincludes authorized geofence notifications listing 6080, which indicatesgeofence notifications that Jane's account has authorized for other useraccounts. As shown in FIG. 6M, the geofence notification listings aregrouped by the user accounts for which the geofence notifications havebeen authorized. For example, geofence notifications listing 6080-1represents a set of four geofence notifications that have beenauthorized for Mom's account. Similarly, geofence notifications listing6080-2 represents a set of two geofence notifications that have beenauthorized for Dad's account, and geofence notifications listing 6080-3represents a single geofence notification that has been authorized forBrother's account.

In FIG. 6M, Jane's device 6000B detects input 6082 on geofencenotifications listing 6080-1 and, in response, displays notificationsdetails user interface 6084, which shows details for the geofencenotifications that have been authorized for Mom's account, as depictedin FIG. 6N.

Notifications details user interface 6084 includes additional detailsfor the geofence notifications authorized for Mom's account. In FIG. 6N,the authorized geofence notifications are grouped based on the useraccount that created the respective notifications. For example, region6086 includes representations of authorized geofence notifications thatwere created by Jane's account. These correspond to geofencenotifications created by Jane's account (e.g., in a manner similar tothat discussed above with respect to FIG. 6B) and authorizing Mom'saccount to be notified when the conditions of the geofence notificationare satisfied. For example, representation 6086-1 corresponds to ageofence notification created by Jane's account that notifies Mom'saccount when Jane's device 6000B leaves its current location.Additionally, representation 6086-2 corresponds to a geofencenotification created by Jane's account that notifies Mom's account whenJane's device 6000B is not located at home between 11 PM and 7 AM.

Notifications details user interface 6084 also includes region 6088 withrepresentations of authorized geofence notifications that were createdby Mom's account. These correspond to geofence notifications created byMom's account (e.g., in a manner similar to that discussed above withrespect to FIG. 6B) and authorized by Jane's account so that Mom'saccount is notified when the conditions of the geofence notification aresatisfied. For example, representation 6088-1 corresponds to thegeofence notification created by Mom's account in FIGS. 6A-6C (andauthorized by Jane's account) that notifies Mom's account when Jane'sdevice 6000B is not located at school between 9 AM and 3 PM weekdays.Additionally, representation 6088-2 corresponds to a geofencenotification created by Mom's account (and authorized by Jane's account)that notifies Mom's account when Jane's device 6000B arrives at home.

In some embodiments, the geofence notifications represented innotifications details user interface 6084 can be de-authorized by Jane'saccount and removed from notifications detail user interface 6084. Forexample, in response to Jane's device 6000B detecting a swipe input onrepresentation 6088-2, Jane's account removes authorization for thecorresponding geofence notification. Accordingly, Jane's device 6000Bremoves representation 6088-2 from notifications details user interface6084 and updates geofence notifications listing 6080-1 to reflect theremoval of the geofence notification (e.g., updating geofencenotification listing 6080-1 to indicate a set of three geofencenotifications are authorized for Mom's account).

FIGS. 6O-6U depict various embodiments illustrating how detected changesin Jane's location (e.g., the location of Jane's device 6000B) satisfy,or fail to satisfy, the conditions of the geofence created in FIGS.6A-6C and authorized by Jane's account in FIG. 6K, and illustratingnotifications that are displayed (e.g., on Mom's device 6000A, Jane'sdevice 6000B, or both) as a result of the detected changes in locationbreaching the geofence.

FIGS. 6O-6Q illustrate an embodiment in which Jane's location breachesthe geofence because Jane's device 6000B is not located at the specifiedlocation of the geofence (e.g., school) at the specified start time(e.g., 9 AM on a weekday). FIG. 6O includes map 6090, which is similarto map 6042 shown in FIG. 6H. Map 6090 includes representation 6092 ofJane's device 6000B, and geofence boundary 6094. As shown in FIG. 6O,representation 6092 of Jane's device is outside geofence boundary 6094at 9:00 AM on Monday. Accordingly, Jane's location breaches thegeofence. As a result, Mom's device 6000A displays notification 6096(e.g., on lock screen user interface 6095) indicating that Jane did notarrive at school by 9 AM.

In some embodiments, Jane's device 6000B displays notification 6098(e.g., on lock screen user interface 6038) to alert Jane that shebreached the geofence and that Mom's account was notified of the breach.In some embodiments, notification 6098 is displayed only the first timeJane breaches the geofence.

In some embodiments, Mom's device 6000A can display different userinterfaces in response to detecting different inputs on a displayednotification (e.g., notification 6096, notification 6120, ornotification 6122). For example, in some embodiments, in response todetecting a tap gesture input on the notification, Mom's device 6000Adisplays locations management user interface 6005. An example of such anembodiment is discussed in greater detail below with reference to FIG.6S. In some embodiments, in response to detecting a long press input onthe notification, Mom's device 6000A displays a popup user interfaceshowing various options that are available in response to Jane's breachof the geofence. An example of such an embodiment is discussed ingreater detail below with reference to FIG. 6O. It should also beappreciated that the notifications can be displayed as other userinterface objects such as, for example, a banner. The notifications canalso be displayed on user interfaces other than lock screen userinterfaces. For example, the user interface can be associated with anapplication operating on electronic device 6000 and the notification isdisplayed as a banner appearing over the user interface at the top ofdisplay 6002.

As illustrated in FIG. 6O, Mom's device 6000A detects long press input6104 on notification 6096 and, in response, displays popup userinterface 6106, as shown in FIG. 6P. Popup user interface 6106 includesvarious selectable options for responding to notification 6096. Forexample, popup user interface 6106 includes map option 6108, contactoption 6110, mute option 6112, “Notify when Jane Arrives” option 6114,and delete option 6116. Map option 6108 includes map 6108-1, which issimilar to map 6090 shown in FIG. 6O, having representation 6108-2 ofJane's device 6000A and geofence boundary 6108-3. Map option 6108 showsJane's location on a map (e.g., at the time notification 6096 wasdisplayed or at the time input 6104 was detected).

In some embodiments, popup user interface 6106 is a user interface thatdisplays a set of options without fully launching an application forperforming the options. However, the options available in popup userinterface 6106 can be selected to launch the application for performingthe selected option. For example, in some embodiments, map option 6108corresponds to an option for launching an application for displaying amap user interface showing a live representation of Jane's location onan expanded map. For example, in response to detecting selection of mapoption 6108, Mom's device 6000A displays locations management userinterface 6005 to show a map user interface (e.g., similar to map 6130shown in locations management user interface 6005 illustrated in FIG.6S) depicting a live representation of Jane's location on a map.

In some embodiments, in response to detecting selection of contactoption 6110, Mom's device 6000A displays one or more options forcontacting Jane's device 6000B (e.g., via phone call, messaging, email,or a video communication session).

In some embodiments, in response to detecting selection of mute option6112, Mom's device 6000A does not display alerts for the geofence forthe remainder of the day. This can be useful for a scenario in which Momis aware that Jane's location will again breach, or will continue tobreach, the geofence (e.g., Jane is on vacation with Mom) and Mom wishesto not be notified of any such future breaches for the remainder of theday.

In some embodiments, in response to detecting selection of delete option6116, Mom's device 6000A dismisses notification 6096 and, in someembodiments, deletes the geofence altogether.

In some embodiments, in response to detecting selection of “Notify whenJane Arrives” option 6114, Mom's device 6000A dismisses notification6096 and later displays a notification if Jane's location matches thelocation specified in the conditions of the geofence. This can be usefulin a scenario in which Mom is aware that Jane will be late to school(e.g., Jane has a doctor's appointment), but wants to know that Janeeventually makes it to school as expected. FIGS. 6P and 6Q illustrate anembodiment in which “Notify when Jane Arrives” option 6114 is selected.

As shown in FIG. 6P, Mom's device 6000A detects input 6118 on “Notifywhen Jane Arrives” option 6114, at 9:00 AM. FIG. 6Q shows Jane arrivingat school an hour later (e.g., at 10:00 AM), and Mom's device 6000Adisplaying notification 6120 informing Mom that Jane has arrived atschool. In some embodiments, Jane's device 6000B does not display anynotifications in this scenario (e.g., lock screen user interface 6038does not include a notification).

FIGS. 6R and 6S illustrate an embodiment in which Jane's locationbreaches the geofence because Jane's device 6000B leaves the specifiedlocation of the geofence (e.g., school) before the specified end time(e.g., 3 PM on a weekday). As shown in FIG. 6R, representation 6092 ofJane's device 6000B is outside geofence boundary 6094 at 2:30 PM onMonday. Accordingly, Jane's location breaches the geofence. As a result,Mom's device 6000A displays notification 6122 indicating that Jane leftschool before 3 PM.

In some embodiments, Jane's device 6000B displays notification 6124 toalert Jane that she breached the geofence and that Mom's account wasnotified of the breach. In some embodiments, notification 6124 isdisplayed only the first time Jane breaches the geofence.

As mentioned above, in some embodiments, Mom's device 6000A can displaydifferent user interfaces in response to detecting different inputs on adisplayed notification. In FIG. 6R, Mom's device 6000A detects tapgesture input 6126 on notification 6122 and, in response, displayslocations management user interface 6005 associated with Mom's account,as shown in FIG. 6S. Locations management user interface 6005 is similarto locations management user interface 6056, which is a locationsmanagement user interface associated with Jane's account. Thus, Mom'sdevice 6000A can perform operations similar to those discussed abovewith respect to locations management user interface 6056. For example,locations management user interface 6005 includes map 6130 showinglocations associated with user accounts that are authorized to sharelocation data with Mom's account, including representation 6132indicating a location on map 6130 that is associated with Jane's account(e.g., a location of Jane's device 6000B), and geofence boundary 6134.As illustrated in FIG. 6S, map 6130 shows that Jane's location isoutside the boundary of the geofence.

Locations management user interface 6005 also includes item 6128associated with Jane's account. In some embodiments, in response todetecting a selection of item 6128, Mom's device 6000A displays Jane'saccount information 6004 (e.g., see FIG. 6A).

FIG. 6T illustrates an embodiment in which Jane's location is inside theboundaries of the geofence during the specified time range and,therefore, is not breaching the geofence. As shown in FIG. 6T,representation 6092 of Jane's device 6000B is inside geofence boundary6094 at 2:30 PM on Monday. Because the geofence is active from 9:00 AMto 3:00 PM on weekdays, Jane's presence at school conforms with theconstraints of the geofence. As such, Jane is not breaching thegeofence. As a result, neither Mom's device 6000A, nor Jane's device6000B, display any notifications concerning a breach of the geofence.Accordingly, lock screen user interface 6095 and lock screen userinterface 6038 do not include any notifications.

FIG. 6U illustrates an embodiment in which Jane's location is outsidethe boundaries of the geofence, but because the time is outside thespecified range, Jane is not breaching the geofence. As shown in FIG.6U, representation 6092 of Jane's device 6000B is outside geofenceboundary 6094 at 3:30 PM on Monday. Because the geofence is active from9:00 AM to 3:00 PM on weekdays, Jane is not breaching the geofence. As aresult, neither Mom's device 6000A, nor Jane's device 6000B, display anynotifications concerning a breach of the geofence. Accordingly, lockscreen user interface 6095 and lock screen user interface 6038 do notinclude any notifications.

It should be appreciated that one or more of the operations disclosedherein (including those discussed below with respect to method 700 andmethod 800) can be performed across various combinations of theelectronic devices discussed herein. For example, in some embodiments,Jane's device 6000B (or Jane's device 6100B) evaluates location data forJane's device, determines when the geofence is breached, and causes thecorresponding notification(s) to be displayed at Mom's device 6000A and,optionally, at Jane's device 6000B. For example, Jane's device can sendthe notification directly to Mom's device 6000A for display, or can sendthe notification indirectly by sending information to a server which, inturn, causes the notification to be displayed at Mom's device 600. Insome embodiments, Mom's device 6000A evaluates location data for Jane'sdevice, determines when the geofence is breached, and causes thecorresponding notification(s) to be displayed at Mom's device 6000A and,optionally, at Jane's device 6000B (e.g., directly or indirectly througha server). In some embodiments, a server evaluates location data forJane's device, determines when the geofence is breached, and causes thecorresponding notification(s) to be displayed at Mom's device 6000A and,optionally, at Jane's device 6000B.

FIG. 7 is a flow diagram illustrating a method for managinglocation-related communications of an electronic device associated witha user account, using an electronic device, in accordance with someembodiments. Method 700 is performed at a device (e.g., 100, 300, 500,6000, 6100B) with a display (e.g., 112). Some operations in method 700are, optionally, combined, the orders of some operations are,optionally, changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for managinglocation-related communications of an electronic device associated witha user account. The method reduces the cognitive burden on a user formanaging location-related communications of an electronic deviceassociated with a user account, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to manage location-related communications of anelectronic device associated with a user account faster and moreefficiently conserves power and increases the time between batterycharges.

While an electronic device (e.g., 6000; 6100) is associated with a firstuser account (e.g. Jane's account) that shares a location of theelectronic device with one or more user accounts other than the firstuser account, the electronic device performs (702) the steps describedbelow.

The electronic device receives (704) an indication (e.g., dataassociated with a request; receiving directly from an externalelectronic device associated with the second user account; receivingfrom a location-tracking server that received the request from theexternal electronic device) that a second user account (e.g., Mom'saccount) (e.g., a remote user or device that has been authorized (e.g.,by the first user account associated with the electronic device) toreceive location data for the electronic device) is requesting to benotified about changes in location of the electronic device relative toa first geographic location (e.g., school) (e.g., a physical address, acoordinate, a defined area or geographic landmark) that satisfy a set ofcriteria (e.g., a set of location-based criteria) (e.g., a set ofcriteria that are evaluated with respect to a predetermined time period(e.g., a range of times)). In some embodiments, the range of times isset by the second user account (e.g., using an external electronicdevice associated with the second user account). In some embodiments,the set of criteria are satisfied when a current location of theelectronic device does not match (or is transitioning from matching tonot matching) the first geographic location. In some embodiments, theset of criteria are satisfied when a current location of the electronicdevice matches (or is transitioning from not matching to matching) thefirst geographic location. In some embodiments, the set of criteria areevaluated based on the current location of the electronic device duringthe predetermined time period.

In some embodiments, the set of criteria include a criterion that issatisfied when the location of the electronic device (e.g., 6000B;6100B) does not have a predefined relationship to the first geographiclocation (e.g., the electronic device is not located at the firstgeographic location) during a range of times (e.g., a range of timesspecified by the first user account) (e.g., a range of times specifiedby the second user account).

In some embodiments, the method further comprises: while the electronicdevice (e.g., 6000B; 6100B) is associated with the first user accountthat shares the location of the electronic device with one or more useraccounts other than the first user account, and while the location ofthe electronic device is being evaluated (e.g., by the electronicdevice; by a server; by a second electronic device associated with thesecond user account) relative to the first geographic location and therange of times, performing one or more of the following steps. Inaccordance with a determination that the location of the electronicdevice does not have the predefined relationship to the first geographiclocation during the range of times (e.g., the electronic device is notlocated at the first geographic location at any point during the rangeof times), generating an alert (e.g., 6096; 6098; 6122; 6124) indicatingthat the location of the electronic device does not have the predefinedrelationship to the first geographic location. In some embodiments,generating the alert includes displaying the alert on the electronicdevice. In some embodiments, generating the alert includes causing thealert to be displayed on an electronic device associated with the seconduser account (e.g., Mom's device 6000A). In accordance with adetermination that the location of the electronic device does not havethe predefined relationship to the first geographic location at a timethat is outside of the range of times (e.g., the electronic device isnot located at the first geographic location at a time that is outsidethe range of times), forgoing generating the alert indicating that thelocation of the electronic device does not have the predefinedrelationship to the first geographic location (e.g., see FIG. 6U).Selectively generating an alert indicating that the location of theelectronic device does not have the predefined relationship to the firstgeographic location provides feedback to a user to indicate when theconditions being evaluated fail to meet a specified criteria. Providingimproved feedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the electronic device is associated with thefirst user account that shares the location of the electronic devicewith one or more user accounts other than the first user account, andwhile the location of the electronic device is being evaluated (e.g., bythe electronic device; by a server; by a second electronic deviceassociated with the second user account) relative to the firstgeographic location and the range of times, the method furthercomprises: in accordance with a determination that the location of theelectronic device has the predefined relationship to the firstgeographic location during the range of times (e.g., the electronicdevice is located at the first geographic location at a time that iswithin the range of times), forgoing generating the alert indicatingthat the location of the electronic device does not have the predefinedrelationship to the first geographic location (e.g., see FIG. 6T).Forgoing generating an alert indicating that the location of theelectronic device does not have the predefined relationship to the firstgeographic location when the location of the electronic device has thepredefined relationship during a range of times provides feedback to auser to indicate when the conditions being evaluated fail to meet aspecified location criteria during a specified range of times. Providingimproved feedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, displaying the notification indicating that thesecond user account is requesting to be notified about changes in thelocation of the electronic device relative to the first geographiclocation that satisfy the set of criteria occurs at a time correspondingto the range of times (e.g., at or near the start of the range of times)(e.g., see display of notification 6040 in FIG. 6G). In someembodiments, the notification is displayed only the first time the starttime of the range of times is reached. In some embodiments, displayingthe notification at a time that matches the start time in the range oftimes provides an enhanced layer of security and preserves privacy ofthe tracked user by providing information that the location of thedevice is being tracked, which is particularly useful in a scenario inwhich a malicious actor has access to the tracked user's device, and themalicious actor sets the geofence and timeframe parameters and, withoutthe tracked user's knowledge or consent, confirms the geofence andtimeframe on the tracked user's device.

In some embodiments, the set of criteria includes a criterion that issatisfied when the location of the electronic device does not match(e.g., or is transitioning from matching to not matching) the firstgeographic location. In some embodiments, the second user accountrequests to be notified when the location of the electronic device isnot at the first geographic location (e.g., during the range of times)(e.g., see FIGS. 6O and 6R).

In some embodiments, the set of criteria includes a criterion that issatisfied when the location of the electronic device matches (e.g., oris transitioning from not matching to matching) the first geographiclocation (e.g., see FIG. 6Q). In some embodiments, the second useraccount is notified (e.g., 6096) when the location of the electronicdevice does not match the first geographic location (e.g., during arange of times) and, in response, the second user account requests to benotified when the electronic device arrives at the first geographiclocation (e.g., during the range of times) (e.g., see input 6118selecting “Notify when Jane Arrives” option 6114 in FIG. 6P).

Method 700 further includes: after the electronic device receives theindication that the second user account is requesting to be notifiedabout changes in the location of the electronic device relative to thefirst geographic location that satisfy the set of criteria, theelectronic device performs (706) one or more of the following steps.

In accordance with a determination that a set of notification criteriaare satisfied, the set of notification criteria including a criterionthat is satisfied when the indication that the second user account isrequesting to be notified has been received, the electronic devicedisplays (708), via the display device, a notification (e.g., 6040,6048) (e.g., an alert, a banner) indicating that the second user accountis requesting to be notified about changes in the location of theelectronic device relative to the first geographic location that satisfythe set of criteria. In some embodiments, the indication includes textidentifying the second user account and/or text describing the set ofcriteria. In some embodiments, the set of notification criteria are metby receiving the indication. In some embodiments, the set ofnotification criteria are met when a location of the electronic devicerelative to the first geographic location satisfies the set of criteriaafter receiving the indication. Displaying a notification indicatingthat the second user account is requesting to be notified about changesin the location of the electronic device relative to the firstgeographic location that satisfy the set of criteria provides feedbackto the user indicating that a remote user account is requesting to uselocation data for notification purposes. Providing improved feedbackenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the one or more user accounts other than the firstuser account includes the second user account (e.g., Mom's account)(e.g., the first user account shares the location of the electronicdevice with the second user account), and the method further comprisesone or more of the following steps. After displaying the notification(e.g., 6040, 6048) indicating that the second user account is requestingto be notified about changes in the location of the electronic devicerelative to the first geographic location that satisfy the set ofcriteria and before authorizing (e.g., granting) the request to be to benotified about changes in the location of the electronic device relativeto the first geographic location that satisfy the set of criteria (e.g.,in some embodiments, after explicitly rejecting the request to benotified about changes in the location of the electronic device relativeto the first geographic location that satisfy the set of criteria):sharing, with the second user account, a location of the electronicdevice. In some embodiments, the first user account continues to sharethe location of the electronic device with the second user account, evenafter the electronic device declines the request to notify the seconduser account about changes in the location of the electronic devicerelative to the first geographical location that satisfy the set ofcriteria. Sharing a location of the electronic device with the seconduser account after displaying the notification, and prior to authorizingthe request to be notified (or after explicitly rejecting the request),permits the user to continue sharing location data with the second useraccount without requiring the user to provide additional input to resumelocation data sharing with the second user account. This reduces thenumber of inputs needed to resume location data sharing with the seconduser account. Reducing the number of inputs needed to perform anoperation enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, after displaying the notification (e.g., 6040,6048) indicating that the second user account is requesting to benotified about changes in the location of the electronic device (e.g.,6000B, 6100B) relative to the first geographic location that satisfy theset of criteria, the method includes one or more of the following steps.In accordance with a determination that a current location of theelectronic device relative to the first geographic location satisfiesthe set of criteria (e.g., during the range of times) and in accordancewith a determination that authorization (e.g., explicit authorizationfor the particular request; pre-authorization based on the identity ofthe requesting device) has been received to notify the second useraccount when a location of the electronic device relative to the firstgeographic location satisfies the set of criteria, notifying (e.g.,displaying notification 6096) (e.g., transmitting data to a deviceassociated with the second user account; transmitting data to anotification server that notifies the second user account) the seconduser account that the current location of the electronic device relativeto the first geographic location satisfies the set of criteria (e.g.,during the range of times (e.g., the location of the electronic deviceis not at the first geographic location at any point during the range oftimes)). In accordance with a determination that a current location ofthe electronic device relative to the first geographic locationsatisfies the set of criteria and in accordance with a determinationthat authorization has not been received to notify the second useraccount when a location of the electronic device relative to the firstgeographic location satisfies the set of criteria, forgoing notifyingthe second user account that the current location of the electronicdevice relative to the first geographic location satisfies the set ofcriteria. Notifying the second user account that the current location ofthe electronic device relative to the first geographic locationsatisfies a set of criteria, when the set of criteria are satisfied andauthorization has been received to notify the second user account,provides an enhanced layer of security and preserves privacy of thefirst user account by requiring authorization for the second useraccount to receive a notification related to the location associatedwith the first user account. Similarly, foregoing notifying the seconduser account that the current location of the electronic device relativeto the first geographic location satisfies a set of criteria, when theset of criteria are satisfied and authorization has not been received tonotify the second user account, provides an enhanced layer of securityand preserves privacy of the first user account by requiringauthorization for the second user account to receive a notificationrelated to the location associated with the first user account.

In some embodiments, displaying the notification (e.g., 6040, 6048)indicating that the second user account is requesting to be notifiedabout changes in the location of the electronic device relative to thefirst geographic location that satisfy the set of criteria occurs whenthe location of the electronic device has a predefined relationship tothe first geographic location (e.g., when the electronic device islocated at the first geographic location) (e.g., see FIG. 6H). In someembodiments, the notification is displayed only the first time theelectronic device is located at the first geographic location. In someembodiments, displaying the notification when the device has thepredefined relationship to the first geographic location provides anenhanced layer of security and preserves privacy of the tracked user byproviding information that the location of the device is being tracked,which is particularly useful in a scenario in which a malicious actorhas access to the tracked user's device, and the malicious actor setsthe geofence and timeframe parameters and, without the tracked user'sknowledge or consent, confirms the geofence and timeframe on the trackeduser's device.

In some embodiments, displaying the notification (e.g., 6040, 6048)indicating that the second user account is requesting to be notifiedabout changes in the location of the electronic device relative to thefirst geographic location that satisfy the set of criteria occurs inresponse to receiving the indication that the second user account isrequesting to be notified about changes in the location of theelectronic device relative to the first geographic location that satisfythe set of criteria (e.g., see FIG. 6F). In some embodiments, the seconduser account (e.g., Mom's account) sets the conditions for the geofence(e.g., as shown in FIGS. 6A-6C) and the electronic device receives theindication (and displays the notification) shortly (e.g., immediately)after the geofence is created.

In some embodiments, after displaying the notification (e.g., 6040,6048) indicating that the second user account is requesting to benotified about changes in the location of the electronic device relativeto the first geographic location that satisfy the set of criteria, themethod further comprises one or more of the following. In accordancewith a determination that authorization (e.g., explicit authorizationfor the particular request; pre-authorization based on the identity ofthe requesting device) has been received to notify the second useraccount when a location of the electronic device relative to the firstgeographic location satisfies the set of criteria, and that a second setof notification criteria are satisfied, the second set of notificationcriteria including a first criterion that is satisfied when the set ofcriteria are satisfied (e.g., the current location of the electronicdevice relative to the first geographic location satisfies the set ofcriteria (e.g., during the range of times)), displaying, via the displaydevice (e.g., 6002), a notification (e.g., 6098, 6124) indicating thatthe location (e.g., current location) of the electronic device relativeto the first geographic location satisfies the set of criteria. In someembodiments, the notification includes text identifying the second useraccount and/or text describing the set of criteria. In some embodiments,displaying the notification informs the user that a notificationconcerning the location of the electronic device is being sent to thesecond user account. This provides an element of privacy for the user bykeeping the user informed of instances in which the user's personalinformation (e.g., location information) is being shared with other useraccounts. In accordance with a determination that authorization has beenreceived to notify the second user account when a location of theelectronic device relative to the first geographic location satisfiesthe set of criteria, and that the second set of notification criteriaare not satisfied, forgoing displaying the notification indicating thatthe location (e.g., current location) of the electronic device relativeto the first geographic location satisfies the set of criteria.

In some embodiments, the second set of notification criteria include asecond criterion that is satisfied when the set of criteria aresatisfied for a first time (e.g., the notification is displayed only thefirst time the set of criteria are satisfied).

In some embodiments, the set of criteria are satisfied when a currentlocation of the electronic device does not have a predefinedrelationship to the first geographical location (e.g., the electronicdevice is not located at the first geographic location) at a start timewithin a range of times (e.g., see FIG. 6O).

In some embodiments, after the electronic device receives the indicationthat the second user account (e.g., Mom's account) is requesting to benotified about changes in the location of the electronic device relativeto the first geographic location that satisfy the set of criteria, andin accordance with a determination that the set of notification criteriaare not satisfied (e.g., a current location of the electronic device(e.g., 6000B, 6100B) relative to the first geographic location fails tosatisfy the set of criteria after receiving the indication), theelectronic device forgoes (710) displaying the notification indicatingthat the second user account is requesting to be notified about changesin the location of the electronic device relative to the firstgeographic location that satisfy the set of criteria (e.g., see Jane'sdevice 6000B-1 in FIG. 6G) (e.g., see Jane's device 6000B-3 in FIG. 6H).

In some embodiments, the method further comprises displaying (e.g.,before receiving the indication; after receiving the indication), viathe display device (e.g., 6002), a notification management interface(e.g., 6072) that includes a set (e.g., 6080) of one or more indications(e.g., 6080-1, 6080-2, 6080-3) that each correspond to a request to benotified about changes in the location of the electronic device relativeto a geographic location.

In some embodiments, the notification management interface includeslocation-based notification information (e.g., 6074, 6076, 6078) (e.g.,address information, map settings, options for sharing locationinformation associated with the first user account) for the first useraccount (e.g., Jane's account).

In some embodiments, the set of one or more indications that eachcorrespond to a request to be notified about changes in the location ofthe electronic device relative to a geographic location is organizedaccording to the user account corresponding (e.g., the user accountmaking the request to be notified; the user account that will benotified) to each indication of the set of one or more indications(e.g., in FIG. 6M, 6080-1 corresponds to Mom's account, 6080-2corresponds to Dad's account, 6080-3 corresponds to Brother's account).In some embodiments, the set of indications include a representation ofthe user account corresponding to set of indications, and arepresentation indication of a number of notifications that areassociated with the user account. Organizing the set of one or moreindications according to the user account corresponding to eachindication of the set of one or more indications provides an organizedand easily navigable user interface that reduces the number of inputsneeded for a user to locate the indications. Reducing the number ofinputs needed for a user to locate the indications enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the set of one or more indications that eachcorrespond to a request to be notified about changes in the location ofthe electronic device relative to a geographic location includes one ormore of the following. A first sub-set of one or more indications (e.g.,6086-1, 6086-2) that each correspond to a request to be notified aboutchanges in the location of the electronic device relative to ageographic location that was created by the first user account (e.g.,Jane's account). A second sub-set of one or more indications (e.g.,6088-1, 6088-2) that each correspond to a request to be notified aboutchanges in the location of the electronic device relative to ageographic location that was created by a user account other than thefirst user account (e.g., Mom's account) (e.g., a user account of theone or more user accounts other than the first user account). In someembodiments, the first sub-set of one or more indications are groupedtogether (e.g., in region 6086) and the second sub-set of one or moreindications are grouped together (e.g., in region 6088) (e.g., andseparate from the first sub-set of one or more indications). Groupingtogether the first and second sub-sets of one or more indicationsprovides an organized and easily navigable user interface that reducesthe number of inputs needed for a user to locate the indications in eachsub-set. Reducing the number of inputs needed for a user to locate theindications enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the method further comprises one or more of thefollowing. While displaying the notification management interface (e.g.,notifications details user interface 6084) (e.g., in some embodiments,notification management user interface 6072 includes notificationsdetails user interface 6084), receiving a first set of one or moreinputs corresponding to a request to de-authorize a first request to benotified about changes in the location of the electronic device relativeto a geographic location. In response to receiving the first set of oneor more inputs: removing authorization for notifications about changesin the location of the electronic device relative to a geographiclocation. In some embodiments, removing authorization for thenotifications includes ceasing to display an indication (e.g., 6086-1,6086-2, 6088-1, 6088-2, 6080-1, 6080-2, 6080-3) of the set of one ormore indications that corresponds to the first request to be notifiedabout changes in the location of the electronic device relative to ageographic location. In some embodiments, the first set of one or moreinputs is a swipe input. In some embodiments, the first set of one ormore inputs is a swipe input on the indication of the set of one or moreindications that corresponds to a request to be notified about changesin the location of the electronic device relative to a geographiclocation followed by a tap gesture on a delete affordance. Removingauthorization for notifications about changes in the location of theelectronic device relative to a geographic location, in response toreceiving the first set of one or more inputs, provides a quick andconvenient method that reduces the number of inputs for removingauthorization for the notification. Reducing the number of inputs neededfor removing authorization for the notification enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7 ) are also applicable in an analogous manner tothe methods described below. For example, method 800 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 700. For example, various steps of method800 are performed after the notification displayed in step 708 has beenaccepted. For brevity, these details are not repeated below.

FIG. 8 is a flow diagram illustrating a method for managinglocation-related communications of an electronic device associated witha user account, using an electronic device, in accordance with someembodiments. Method 800 is performed at a device (e.g., 100, 120, 300,310, 500, 516, 6000, 6100B). Some operations in method 800 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 800 provides an intuitive way for managinglocation-related communications of an electronic device associated witha user account. The method reduces the cognitive burden on a user formanaging location-related communications of an electronic deviceassociated with a user account, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to manage location-related communications of anelectronic device associated with a user account faster and moreefficiently conserves power and increases the time between batterycharges.

Method 800 includes performing one or more of the following steps at anelectronic device (e.g., a server) (e.g., an electronic device having adisplay device (e.g., a touch-sensitive display) (e.g., Jane's device6000B; Jane's device 6100B) (e.g., Mom's device 6000A). In someembodiments, the electronic device is associated with a user account(e.g., a child's account; Jane's account) for which a current locationis being evaluated. In some embodiments, the electronic device isassociated with a second user account (e.g., a parent's user account;Mom's account) that is authorized to receive location data for anelectronic device (e.g., Jane's device 6000B; Jane's device 6100B)associated with the user account (e.g., the child's user account) forwhich the current location is being evaluated. In some embodiments, theelectronic device is a server that is authorized to receive locationdata for an electronic device (e.g., Jane's device 6000B; Jane's device6100B) associated with the user account (e.g., Jane's account) for whichthe current location is being evaluated.

Method 800 includes performing (802) one or more of the following stepswhile a current location associated with a user account (e.g., Jane'saccount) (e.g., a current location of an electronic device associatedwith the user account) is being evaluated (e.g., tracked or monitored)relative to a geographic location (e.g., school) (e.g., a physicaladdress, a coordinate, a defined area, or a geographic landmark) and arange of times (e.g., between 9:00 AM and 3:00 PM on weekdays) (e.g., arange of times specified by the user account) (e.g., a range of timesspecified by the second user account (e.g., Mom's account)).

In accordance with a determination that the current location associatedwith the user account does not have a predefined relationship to thegeographic location during the range of times (e.g., the electronicdevice associated with the user account is not located at the geographiclocation at any point during the range of times), the electronic devicegenerates (804) an alert (e.g., a notification such as a pop up or abanner) (e.g., 6096, 6098, 6122, 6124) indicating that the currentlocation associated with the user account (e.g., Jane's account) doesnot have the predefined relationship to the geographic location (e.g.,school) (e.g., see FIG. 6O) (e.g., see FIG. 6R). In some embodiments,generating the alert includes displaying the alert on the electronicdevice (e.g., when the electronic device is associated with the useraccount (e.g., child account) or is associated with the second useraccount (e.g., parent account)). In some embodiments, generating thealert includes causing an external electronic device to display thealert (e.g., when the electronic device is a server). In someembodiments, the external electronic device is an electronic deviceassociated with the user account. In some embodiments, the externalelectronic device is an electronic device associated with the seconduser account. Generating an alert indicating that the current locationassociated with the user account does not have the predefinedrelationship to the geographic location, when the current location doesnot have the predefined relationship at a time within the range oftimes, provides feedback to a user indicating that the conditions beingevaluated violate a specified criteria. Providing improved feedbackenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the user account has the predefined relationship tothe geographic location when the current location associated with theuser account matches (e.g., or is transitioning from not matching tomatching) the geographic location (e.g., see FIG. 6T).

In some embodiments, the alert is generated on a first date (e.g.,Monday, June 3rd, as shown in FIG. 6O), and the alert includes a firstuser interface object (e.g., a “Mute for Today” affordance; mute option6112) that, when selected, initiates a process for preventing display ofsubsequent alerts generated on the first date and associated with theevaluation of the current location associated with the user accountrelative to the geographic location during the range of times (e.g.,when the first user interface object is selected, future alerts for thegeofence and range of times are not displayed for the remainder of theday). In some embodiments, the first user interface object is displayedin response to long press input 6104 on notification 6096.

In some embodiments, the alert includes a second user interface object(e.g., a “Contact” affordance; contact option 6110) that, when selected,initiates a process for contacting (e.g., calling, emailing, messaging,video conferencing) an external electronic device (e.g., Jane's device6000B; Jane's device 6100B) associated with the user account (e.g.,Jane's account). In some embodiments, the second user interface objectis displayed in response to long press input 6104 on notification 6096.

In some embodiments, the alert includes a third user interface object(e.g., a “Notify when Jane Arrives” affordance; “Notify when JaneArrives” option 6114) that, when selected, initiates a process for:while the current location associated with the user account is beingevaluated relative to the geographic location during the range of timesand in accordance with a determination that the current locationassociated with the user account has the predefined relationship to thegeographic location (e.g., during the range of times) (e.g., at a timeoutside the range of times), generating a second alert (e.g., 6120)indicating that the current location associated with the user accounthas the predefined relationship to the geographic location (e.g.,generating the second alert when the electronic device associated withthe user account is located at the geographic location or istransitioning from a location that does not match the geographiclocation to a location that does match the geographic location) (e.g.,see FIG. 6Q). In some embodiments, the third user interface object isdisplayed in response to long press input 6104 on notification 6096.Generating a second alert indicating that the current locationassociated with the user account has the predefined relationship to thegeographic location provides feedback to a user indicating that theconditions being evaluated are now satisfied, when they previously werenot satisfied. Providing improved feedback enhances the operability ofthe device and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the alert includes a fourth user interface object(e.g., a map affordance; map option 6108) that, when selected, initiatesa process for displaying a map representing the current locationassociated with the user account (e.g., associated with an externalelectronic device associated with the user account). In someembodiments, the alert includes a representation of the map (e.g.,6108-1) (e.g., the fourth user interface object is the representation ofthe map representing a location associated with the user account), andthe map displayed in response to selecting the fourth user interfaceobject includes an expanded map or an option to view an expanded map. Insome embodiments, the fourth user interface object is displayed inresponse to long press input 6104 on notification 6096.

In some embodiments, the alert (e.g., 6096) is generated when thecurrent location associated with the user account does not match thegeographic location at a start time of the range of times (e.g., thealert is generated when the time period starts and the electronic deviceassociated with the user account is not located within the geofence)(e.g., see FIG. 6O). In some embodiments, the determination that thecurrent location associated with the user account does not have apredefined relationship to the geographic location during the range oftimes includes a determination that the current location associated withthe user account does not match the geographic location at a start timeof the range of times.

In some embodiments, the alert (e.g., 6122, 6124) is generated when thecurrent location associated with the user account transitions fromhaving the predefined relationship to the geographic location during therange of times to not having the predefined relationship to thegeographic location during the range of times (e.g., the alert isgenerated when the electronic device associated with the user accountleaves the geofence during the time period) (e.g., see FIG. 6R). In someembodiments, the determination that the current location associated withthe user account does not have a predefined relationship to thegeographic location during the range of times includes a determinationthat the current location associated with the user account hastransitioned from having the predefined relationship to the geographiclocation during the range of times to not having the predefinedrelationship to the geographic location during the range of times.

In accordance with a determination that the current location associatedwith the user account does not have a predefined relationship to thegeographic location at a time that is outside of the range of times(e.g., the electronic device associated with the user account is notlocated at the geographic location at a time that is outside the rangeof times), the electronic device forgoes (806) generating an alertindicating that the current location associated with the user accountdoes not have the predefined relationship to the geographic location(e.g., see FIG. 6U). Foregoing generating an alert indicating that thecurrent location associated with the user account does not have thepredefined relationship to the geographic location, when the currentlocation does not have the predefined relationship at a time outside ofthe range of times, provides feedback (by not generating the alert) to auser indicating that the conditions being evaluated do not violate aspecified criteria. Providing improved feedback enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the current location associated with the useraccount (e.g., Jane's account) is being evaluated (e.g., tracked ormonitored) relative to the geographic location (e.g., school) and therange of times (e.g., between 9:00 AM and 3:00 PM on weekdays), inaccordance with a determination that the current location associatedwith the user account has a predefined relationship to the geographiclocation at a time that is outside of the range of times (e.g., theelectronic device associated with the user account is located at thegeographic location at a time that is outside the range of times) (e.g.,Jane's device 6000B is located at school at 3:30 PM on Monday), theelectronic device foregoes (808) generating an alert indicating that thecurrent location associated with the user account does not have thepredefined relationship to the geographic location. Foregoing generatingan alert indicating that the current location associated with the useraccount does not have the predefined relationship to the geographiclocation, when the current location does have the predefinedrelationship at a time outside of the range of times, provides feedback(by not generating the alert) to a user indicating that the conditionsbeing evaluated do not violate a specified criteria. Providing improvedfeedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while the current location associated with the useraccount is being evaluated (e.g., tracked or monitored) relative to thegeographic location and the range of times, in accordance with adetermination that the current location associated with the user accounthas a predefined relationship to the geographic location during therange of times (e.g., the electronic device associated with the useraccount is located at the geographic location at a time that is withinthe range of times), the electronic device foregoes (810) generating analert indicating that the current location associated with the useraccount does not have the predefined relationship to the geographiclocation (e.g., see FIG. 6T). Foregoing generating an alert indicatingthat the current location associated with the user account does not havethe predefined relationship to the geographic location, when the currentlocation does have the predefined relationship at a time within of therange of times, provides feedback (by not generating the alert) to auser indicating that the conditions being evaluated do not violate aspecified criteria. Providing improved feedback enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the electronic device (e.g., 6000) has a displaydevice (e.g., 6002) (e.g., a touch-sensitive display) (e.g., at anelectronic device associated with a second user account (e.g., Mom'sdevice 6000A), and the method further comprises performing one or moreof the following steps. Prior to the current location associated withthe user account (e.g., Jane's account) being evaluated relative to thegeographic location and the range of times (e.g., and while the useraccount shares a location of an electronic device associated with theuser account with one or more user accounts other than the user account(e.g., Mom's account)), displaying, via the display device, thefollowing: 1) a location user interface object (e.g., 6016-2) that, whenselected, initiates a process for specifying the geographic location; 2)a date user interface object (e.g., 6020-1 through 6020-7) that, whenselected, initiates a process for specifying a date component of therange of times; and 3) a time user interface object (e.g., 6018-1,6018-2) that, when selected, initiates a process for specifying a timecomponent of the range of times. In some embodiments, the boundary ofthe geofence is setup by detecting user selection of the location userinterface object. In some embodiments, this includes receiving userinput including location information such as an address, a coordinate, adefined area on a map, or a geographic landmark. In some embodiments,the user can view the geographic location on a map and manipulate themap to adjust the boundaries of the geofence (e.g., by adjusting a zoomlevel of the map). In some embodiments, the range of times is set up bydetecting user selection of the date user interface object and time userinterface object. In some embodiments, this includes detecting a userselection of a date on which the range of times should begin. In someembodiments, this includes detecting a user selection of particular daysof the week for which the range of times should repeat (e.g., selectingoptions for repeating the range of times from Monday through Friday, butnot on Saturday or Sunday). In some embodiments, this includes detectinga user selection of a start time and an end time for the range of times(e.g., start at 9:00 AM and end at 3:00 PM).

In some embodiments, prior to the current location associated with theuser account (e.g., Jane's account) being evaluated relative to thegeographic location and the range of times (e.g., and while the useraccount shares a location of an electronic device associated with theuser account with one or more user accounts other than the useraccount), the electronic device generates (and, in some embodiments,transmits; causes to be transmitted) a notification (e.g., 6040, 6048)for display at an external electronic device (e.g., Jane's device 6000B,Jane's device 6100B) associated with the user account, the notificationincluding an indication (e.g., text 6048-1) that a second user account(e.g., a remote user or device that has been authorized (e.g., by theuser account associated with the electronic device) to receive locationdata associated with the user account; a user account associated withthe electronic device) is requesting to be notified about changes in thelocation associated with the user account relative to the geographiclocation during the range of times. In some embodiments, the electronicdevice associated with the user account is a first electronic device(e.g., Jane's device 6000B). In some embodiments, the electronic deviceassociated with the user account is a second electronic device (e.g.,Jane's device 6100B) different from the first electronic device. In someembodiments, the notification is the notification displayed in step 708discussed above with respect to method 700. Generating a notificationincluding an indication that a second user account is requesting to benotified about changes in the location associated with the user accountrelative to the geographic location during the range of times providesan enhanced layer of security and preserves privacy of the tracked userby providing an indication to the user that another user account isintending to receive notifications related to the location associatedwith the user account.

In some embodiments, the notification (e.g., 6040, 6048) is generated inresponse to a determination that the current location associated withthe user account (e.g., Jane's account) has the predefined relationshipto the geographic location during the range of times (e.g., theelectronic device associated with the user count is located at thegeographic location without consideration of the range of times) (e.g.,see FIG. 6H). In some embodiments, the notification is generated onlythe first time the location of the user account has the predefinedrelationship to the geographic location. In some embodiments, generatingthe notification when the device has the predefined relationship to thegeographic location provides an enhanced layer of security and preservesprivacy of the tracked user by providing information that the locationof the device is being tracked, which is particularly useful in ascenario in which a malicious actor has access to the tracked user'sdevice, and the malicious actor sets the geofence and timeframeparameters and, without the tracked user's knowledge or consent,confirms the geofence and timeframe on the tracked user's device.

In some embodiments, the notification is generated at a time thatcorresponds to (e.g., matches the start of) the range of times (e.g.,the notification is generated at, or near, the start of the range oftimes) (e.g., see FIG. 6G). In some embodiments, the notification isgenerated only the first time the start time of the range of times isreached. In some embodiments, generating the notification at a time thatmatches the start time in the range of times provides an enhanced layerof security and preserves privacy of the tracked user by providinginformation that the location of the device is being tracked, which isparticularly useful in a scenario in which a malicious actor has accessto the tracked user's device, and the malicious actor sets the geofenceand timeframe parameters and, without the tracked user's knowledge orconsent, confirms the geofence and timeframe on the tracked user'sdevice.

Note that details of the processes described above with respect tomethod 800 (e.g., FIG. 8 ) are also applicable in an analogous manner tothe methods described above. For example, method 700 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 800. For example, various steps of method800 are performed after acceptance of the notification displayed in step708 of method 700. For brevity, these details are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve themanagement of location-related communications of electronic devices. Thepresent disclosure contemplates that in some instances, this gathereddata may include personal information data that uniquely identifies orcan be used to contact or locate a specific person. Such personalinformation data can include demographic data, location-based data,telephone numbers, email addresses, twitter IDs, home addresses, data orrecords relating to a user's health or level of fitness (e.g., vitalsigns measurements, medication information, exercise information), dateof birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used totrack locations of a user device. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure. For instance, health and fitness data may be used toprovide insights into a user's general wellness, or may be used aspositive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof tracking the location of an electronic device, the present technologycan be configured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In another example,users can select not to provide certain location data for specifiedtimeframes. In addition to providing “opt in” and “opt out” options, thepresent disclosure contemplates providing notifications relating to theaccess or use of personal information. For instance, a user may benotified upon downloading an app that their personal information datawill be accessed and then reminded again just before personalinformation data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data.

What is claimed is:
 1. An electronic device, comprising: one or moreprocessors; and memory storing one or more programs configured to beexecuted by the one or more processors, the one or more programsincluding instructions for: while a current location associated with auser account is being evaluated relative to a geographic location and arange of times: in accordance with a determination that the currentlocation associated with the user account does not have a predefinedrelationship to the geographic location during the range of times,generating an alert indicating that the current location associated withthe user account does not have the predefined relationship to thegeographic location; and in accordance with a determination that thecurrent location associated with the user account does not have apredefined relationship to the geographic location at a time that isoutside of the range of times, forgoing generation of an alertindicating that the current location associated with the user accountdoes not have the predefined relationship to the geographic location. 2.The electronic device of claim 1, the one or more programs furtherincluding instructions for: while the current location associated withthe user account is being evaluated relative to the geographic locationand the range of times: in accordance with a determination that thecurrent location associated with the user account has a predefinedrelationship to the geographic location at a time that is outside of therange of times, forgoing generation of an alert indicating that thecurrent location associated with the user account does not have thepredefined relationship to the geographic location.
 3. The electronicdevice of claim 1, the one or more programs further includinginstructions for: while the current location associated with the useraccount is being evaluated relative to the geographic location and therange of times: in accordance with a determination that the currentlocation associated with the user account has a predefined relationshipto the geographic location during the range of times, forgoinggeneration of an alert indicating that the current location associatedwith the user account does not have the predefined relationship to thegeographic location.
 4. The electronic device of claim 1, furthercomprising a display device, the one or more programs further includinginstructions for: prior to the current location associated with the useraccount being evaluated relative to the geographic location and therange of times: displaying via the display device: a location userinterface object that, when selected, initiates a process for specifyingthe geographic location; a date user interface object that, whenselected, initiates a process for specifying a date component of therange of times; and a time user interface object that, when selected,initiates a process for specifying a time component of the range oftimes.
 5. The electronic device of claim 1, the one or more programsfurther including instructions for: prior to the current locationassociated with the user account being evaluated relative to thegeographic location and the range of times: generating a notificationfor display at an external electronic device associated with the useraccount, the notification including an indication that a second useraccount is requesting to be notified about changes in the locationassociated with the user account relative to the geographic locationduring the range of times.
 6. The electronic device of claim 5, whereinthe notification is generated in response to a determination that thecurrent location associated with the user account has the predefinedrelationship to the geographic location during the range of times. 7.The electronic device of claim 5, wherein the notification is generatedat a time that corresponds to the range of times.
 8. The electronicdevice of claim 1, wherein: the alert is generated on a first date, andthe alert includes a first user interface object that, when selected,initiates a process for preventing display of subsequent alertsgenerated on the first date and associated with the evaluation of thecurrent location associated with the user account relative to thegeographic location during the range of times.
 9. The electronic deviceof claim 1, wherein the alert includes a second user interface objectthat, when selected, initiates a process for contacting an externalelectronic device associated with the user account.
 10. The electronicdevice of claim 1, wherein the alert includes a third user interfaceobject that, when selected, initiates a process for: while the currentlocation associated with the user account is being evaluated relative tothe geographic location during the range of times and in accordance witha determination that the current location associated with the useraccount has the predefined relationship to the geographic location,generating a second alert indicating that the current locationassociated with the user account has the predefined relationship to thegeographic location.
 11. The electronic device of claim 1, wherein thealert includes a fourth user interface object that, when selected,initiates a process for displaying a map representing the currentlocation associated with the user account.
 12. The electronic device ofclaim 1, wherein the alert is generated when the current locationassociated with the user account does not match the geographic locationat a start time of the range of times.
 13. The electronic device ofclaim 1, wherein the alert is generated when the current locationassociated with the user account transitions from having the predefinedrelationship to the geographic location during the range of times to nothaving the predefined relationship to the geographic location during therange of times.
 14. The electronic device of claim 1, wherein the useraccount has the predefined relationship to the geographic location whenthe current location associated with the user account matches thegeographic location.
 15. A non-transitory computer-readable storagemedium storing one or more programs configured to be executed by one ormore processors of an electronic device, the one or more programsincluding instructions for: while a current location associated with auser account is being evaluated relative to a geographic location and arange of times: in accordance with a determination that the currentlocation associated with the user account does not have a predefinedrelationship to the geographic location during the range of times,generating an alert indicating that the current location associated withthe user account does not have the predefined relationship to thegeographic location; and in accordance with a determination that thecurrent location associated with the user account does not have apredefined relationship to the geographic location at a time that isoutside of the range of times, forgoing generation of an alertindicating that the current location associated with the user accountdoes not have the predefined relationship to the geographic location.16. A method, comprising: at an electronic device: while a currentlocation associated with a user account is being evaluated relative to ageographic location and a range of times: in accordance with adetermination that the current location associated with the user accountdoes not have a predefined relationship to the geographic locationduring the range of times, generating an alert indicating that thecurrent location associated with the user account does not have thepredefined relationship to the geographic location; and in accordancewith a determination that the current location associated with the useraccount does not have a predefined relationship to the geographiclocation at a time that is outside of the range of times, forgoinggeneration of an alert indicating that the current location associatedwith the user account does not have the predefined relationship to thegeographic location.